home *** CD-ROM | disk | FTP | other *** search
/ NetNews Offline 2 / NetNews Offline Volume 2.iso / news / comp / std / c++ / 539 < prev    next >
Encoding:
Internet Message Format  |  1996-08-06  |  1.4 KB
  1. Path: engnews1.Eng.Sun.COM!taumet!clamage
  2. From: vandevod@cs.rpi.edu (David Vandevoorde)
  3. Newsgroups: comp.std.c++
  4. Subject: Re: The realloc question: rationale?
  5. Date: 26 Feb 1996 01:33:33 GMT
  6. Organization: RPI Computer Science
  7. Sender: vandevod@glob.cs.rpi.edu
  8. Approved: clamage@eng.sun.com (comp.std.c++)
  9. Message-ID: <xsod973w4m5.fsf@glob.cs.rpi.edu>
  10. References: <4g903m$7g8@mari.onr.com> <4gl2ad$lqi@hermes.synopsys.com>
  11.     <31301BFE.450A@onr.com>
  12. NNTP-Posting-Host: taumet.eng.sun.com
  13. X-Nntp-Posting-Host: glob.cs.rpi.edu
  14. In-Reply-To: Kerry Kimbrough's message of 25 Feb 1996 16:44:48 GMT
  15. X-Newsreader: Gnus v5.1
  16. Originator: clamage@taumet
  17.  
  18. >>>>> "KK" == Kerry Kimbrough <kk@onr.com> writes:
  19. KK> Joe Buck wrote:
  20. KK>>  You can, of course, call the C realloc().
  21.  
  22. KK> But then crash? My understanding is that mixture of alloc/free and
  23. KK> friends with new/delete is not guaranteed to be valid and
  24. KK> therefore is discouraged.  Not true?
  25. [...]
  26.  
  27. Since you can provide your own new operators etc., you can ensure that
  28. it's safe to use realloc with new/delete (or you can provide a function
  29. based on realloc with similar functionality).
  30.  
  31.     Daveed
  32.  
  33. [ To submit articles: Try just posting with your newsreader.
  34.               If that fails, use mailto:std-c++@ncar.ucar.edu
  35.   FAQ:    http://reality.sgi.com/employees/austern_mti/std-c++/faq.html
  36.   Policy: http://reality.sgi.com/employees/austern_mti/std-c++/policy.html
  37.   Comments? mailto:std-c++-request@ncar.ucar.edu
  38. ]
  39.